- 
                Notifications
    You must be signed in to change notification settings 
- Fork 176
chore(deps-dev): bump the vitest group across 1 directory with 2 updates #4679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
c1cc3b4    to
    5a01648      
    Compare
  
    Bumps the vitest group with 2 updates in the / directory: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/coverage-v8` from 3.2.4 to 4.0.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.1/packages/coverage-v8) Updates `vitest` from 3.2.4 to 4.0.1 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.1/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.0.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: vitest - dependency-name: vitest dependency-version: 4.0.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: vitest ... Signed-off-by: dependabot[bot] <[email protected]>
5a01648    to
    b32a19f      
    Compare
  
    | Some of the tests were failing because of the vitest upgrade. Will look into this | 
| After fixing the failing tests which were because of not awaiting the  | 
| 
 | 



Bumps the vitest group with 2 updates in the / directory: @vitest/coverage-v8 and vitest.
Updates
@vitest/coverage-v8from 3.2.4 to 4.0.1Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
4a28faachore: release v4.0.1da7ce17chore: release v4.0.03e4b6b7chore: release v4.0.0-beta.1935816fefix(coverage): v8 to ignore Vite's generated cjs import helpers (#8718)bc7c20dchore: release v4.0.0-beta.184783137chore: release v4.0.0-beta.176fc7890chore: release v4.0.0-beta.16d677c0bchore: release v4.0.0-beta.15e24e56bchore: release v4.0.0-beta.140dc93eafeat: introduce separate packages for browser mode providers (#8629)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@vitest/coverage-v8since your current version.Updates
vitestfrom 3.2.4 to 4.0.1Release notes
Sourced from vitest's releases.
... (truncated)
Commits
4a28faachore: release v4.0.13fae73efix(pool): don't teardown the communication channel too soon if something is ...8100063fix: move thegetBuiltinscheck (#8765)da7ce17chore: release v4.0.08e15bc8perf: create only one fetcher per project (#8762)9f0ecccfix:baseoption doesn't crash vitest (#8760)d3ef4f2perf(pool): resolve all environments first (#8759)08498f0fix(pool): properly reuse the vm pool (#8758)bab343bchore: remove useless comments3e4b6b7chore: release v4.0.0-beta.19Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions